| The GlassFish project is migrating from IssueTracker to JIRA. The two bug tracking system have similarities as well as differences. JIRA allows some of the fields and workflow to be customized. This page compares the two tools and makes recommendations for customizations to JIRA. Issue Type
| IssueTracker |
JIRA Default |
Proposed Default |
| Defect |
Bug |
|
| Enhancement |
Improvement |
|
| Feature |
New Feature |
|
| Task |
Task |
|
| Patch |
|
|
Priority
| IssueTracker |
JIRA Default |
Proposed Default |
| P1 |
Blocker |
|
| P2 |
Critical |
|
| P3 |
Major |
|
| P4 |
Minor |
|
| P5 |
Trivial |
|
Status / Lifecycle
| IssueTracker |
JIRA Default |
Proposed Default |
| UNCONFIRMED |
Open |
|
| NEW |
Open |
|
| STARTED |
In Progress |
|
| RESOLVED |
Resolved |
|
| REOPENED |
Reopened |
|
| VERIFIED |
|
|
| CLOSED |
Closed |
|
Resolved State
| IssueTracker |
JIRA Default |
Proposed Default |
| FIXED |
Fixed |
|
| INVALID |
|
|
| WONTFIX |
Won't Fix |
|
| LATER |
|
|
| REMIND |
|
|
| DUPLICATE |
Duplicate |
|
| WORKSFORME |
Cannot Reproduce |
|
| |
Incomplete |
|
Affects Version/Found in Version When submitting an issue in IssueTracker one can only choose from a small set of base releases: 3.1, 3.2, 4.0, 9.0pe, 9.0peur1, 9.1.1, 9.1pe, 9.1peur1, 9.1peur2, v2.1, v2.1.1, v2.1.2, v2.2, V3, v3.0.1 In IssueTracker's "Enter Issue" interface this field is called: "Found in version". When creating a new issue in JIRA two fields are presented to the submitter:
- Affects Version/s: this is the version(s) in which the issue is manifesting. For instance, a software bug might affect versions 1.1 and 1.2.
- Fix Version/s: this is the version(s) in which the issue was (or will be) fixed. For instance, the bug affecting versions 1.1 and 1.2 might be fixed in version 2.0. Note that issues which do not have a Fix Version are classified as 'Unscheduled'.
Both fields in JIRA are currently populated with the same values. The values appear to be copied from IssueTracker's "Target Milestone" field. There is about 100 values here (e.g. 9.1pe_b34, etc). We should reduce the number of available choices. We should consider changing:
- "Affects Version/s" to "Found in version(s)"
- "Fix Version/s" to "Fixed in version(s)"
It is not clear why "Fix Version/s" is exposed in the "create issue" interface. OS/Platform In IssueTracker the OS and Platform are entered via predefined pull down lists. In JIRA OS and Platform information is entered in a free-form text field called "Environment" with the follow sub-text: "For example operating system, software platform and/or hardware specifications (include as appropriate for the issue)." Keywords, Tags, Whiteboard In IssueTracker one cannot control the Keywords or Whiteboard when submitting an issue. They can be added/modified via the edit issue interface. In IssueTracker Keywords must match a set of predefined values. The Whiteboard field is open to any values. In JIRA the Tags and Whiteboard area can be filled in at issue creation. The user can provide any values in either field. What's the difference between Tags and Whiteboard items in JIRA? It appears a tag becomes a live link which can be used to find other issues tagged with the same value. In JIRA it is not clear how one finds the set of Tags which are current in use. Issue Creation It appears in JIRA one can create an issue by only providing a summary. All other values will default or not be provided in the initial issue. At issue creation one can also provide a "Due Date" (Date) as well as an "Original Estimate" which is expected to be in the form of #d or #w or #m (e.g. 1d, 3w, 5m). Not clear if this will be useful to us? Notifications Notification are currently turned off in JIRA so it is difficult to get a sense for how this works. When I change the state of an issue or update a comment, etc it is not clear who will see the update. I suspect it is those users who are watching the issue as well as the submitter and assignee. In IssueTracker one can add users to the CC field to ensure they are notified of changes. I could not find a way to add users to the watch list for an issue in JIRA. A user can choose to add theirself to the watch list but it doesn't appear I can add other users. Depends on/Blocks In IssueTracker one can link bugs by indicating it depends on other issues or blocks other issues. IssueTracker provides a link to see the dependency tree of an issue. In JIRA there is a "Link Issue" page which allows a user to link issues. When linking an issue they can choose the type of link:
- depends on
- blocks
- duplicates
- is duplicated by
This creates the relationship which becomes visible in both issues. Duplicating an Issue In IssueTracker when an issue is resolved as a duplicate one needs to provide the issue id of the issue that is duplicated. In JIRA one can choose the Close or Resolve workflow and choose Duplicate as the resolution but not be required to enter an issue id to identify the issue that is duplicated. As a separate (optional) step one needs to use the Link Issue functionality to link the issue to another and then switch back to the Close/Resolve workflow to resolve the issue. General UI From the Issues UI can not find a field to enter an issue (e.g. GLA-13515) to jump directly to that issue. - I found it - Use the "Quick Search" field in the upper right of the interface. |
